Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed exception code and status code of response when invalid geometry is inserted #703

Merged
merged 1 commit into from
Aug 17, 2016

Conversation

dstenger
Copy link
Contributor

@dstenger dstenger commented Jun 3, 2016

This fix targets the transaction functionality of WFS 2.0.0.

Previously, when transactions were done with invalid geometries, the WFS 2.0.0 threw an NoApplicableCode exception with status code 500.

The specification says that following is expected:

  • status code: 400
  • exception code: InvalidValue

Excerpt from WFS 2.0.0 specification:

15.2.5.2.1 Property element

In all cases, if the specified action results in invalidating the feature instance 
according to the feature type schema obtained using a DescribeFeatureType operation 
(see Clause 9), the server shall raise a InvalidValue exception (see 7.5).

This fix corrects the status and exception codes to implement the expected behaviour.

In addition, deegree now passes following test of the CITE WFS 2.0 test suite (Transactional CC) [1]:

  • "Update Bounded By With K M L Point"

[1] http://cite.opengeospatial.org/teamengine/

@dstenger dstenger added bug error issue and bug (fix) in progress labels Jun 3, 2016
@tfr42 tfr42 added this to the 3.4 milestone Jun 10, 2016
@copierrj copierrj merged commit ec9791e into deegree:master Aug 17, 2016
@lgoltz lgoltz deleted the exceptionInvalidPoint-3499 branch December 8, 2022 09:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug error issue and bug (fix)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants